Ground lock control
Function Introduction
Ground lock control
explanation
Request message style
{ "operator": "GroundLockControl", "sessionId": "SID:1234567890-000001", "messageId": "MID:localhost-122334455667-12232323232323-000001", "info": { "command": 1, "parkingSpaceName": "YB-001", "parkingSpaceNumber": 1, "force": 1 } }
Request message parameters
Message field name | description | Required |
---|---|---|
deviceinfo | ||
serialNumber | Device serial number | Yes |
platformID | platform ID | No |
info | ||
command | Control ground lock command, 0 - down; 1 - up | Yes |
parkingSpaceName | Parking space name | Yes |
parkingSpaceNumber | Parking space number | Yes |
force | Whether to force operation (lift lock), 0 - No; 1 - Yes | Yes |
Response message style
{ "operator": "GroundLockControl-Ack", "sessionId": "SID:1234567890-000001", "messageId": "MID:localhost-122334455667-12232323232323-000001", "info": "none", "result": { "errorNo": 0, "description": "ok" } }
Response message parameters
Ground lock status change event
Function Introduction
Ground lock status change event
explanation
- 1. This event supports power-off retransmission
- 2. When the event response interval is exceeded, the event will be retransmitted
Request message style
{ "operator": "GroundLockStatusChanged", "sessionId": "SID:1234567890-000001", "messageId": "MID:localhost-122334455667-12232323232323-000001", "deviceInfo": { "serialNumber": "I320013590DEA0BE21F6958", "platformId": "1234556666" }, "info": { "eventId": 1, "time": "20200331T10:10:01+08:00", "groundLockStatus": 1, "parkingSpaceName": "YB-001", "parkingSpaceNumber": 1, "force": 1 } }
Request message parameters
Message field name | description | Required |
---|---|---|
deviceinfo | ||
serialNumber | Device serial number | Yes |
platformID | platform ID | No |
info | ||
eventId | Event ID. For the same event, the ID is the same | Yes |
time | The time when the event occurred, in accordance with the ISO 8601 time format. Please refer to the ISO8601 standard for the combination of date and time. | Yes |
groundLockStatus | Ground lock status, 0 - down; 1 - up | Yes |
parkingSpaceName | Parking space name | Yes |
parkingSpaceNumber | Parking space number | Yes |
force | Whether to force the operation, 0 - No; 1 - Yes | Yes |
Response message style
{ "operator": "GroundLockStatusChanged-Ack", "sessionId": "SID:1234567890-000001", "messageId": "MID:localhost-122334455667-12232323232323-000001", "info": { "eventId": 1 }, "result": { "errorNo": 0, "description": "ok" } }
Response message parameters
Message field name | description | Required |
---|---|---|
eventId | Event ID. For the same event, the ID is the same | Yes |
Ground lock lifting strategy
Function Introduction
Ground lock lifting strategy
explanation
Request message style
{ "operator": "GroundlockLiftStrategy", "sessionId": "SID:1234567890-000001", "messageId": "MID:localhost-122334455667-12232323232323-000001", "deviceInfo": { "serialNumber": "I320013590DEA0BE21F6958", "platformId": "1234556666" }, "info": { "heartbeatInterval": 15, "bearOffLiftLockDuration": 20, "lockEnabledDate0": 65535, "lockEnabledDate1": 65535, "lockEnabledDate2": 65535, "localWhiteList": { { "plate": "44_AT8888", "localWhiteOpt": 0 } }, "localWhiteNum": 1, "authMode": 0, "taskPhotosDuration": 10, "buzzer": 0 } }
Request message parameters
Message field name | description | Required |
---|---|---|
deviceinfo | ||
serialNumber | Device serial number | Yes |
platformID | platform ID | No |
info | ||
heartbeatInterval | Heartbeat reporting frequency interval (seconds), default 15s, range: 15-180 | Yes |
bearOffLiftLockDuration | The time to unlock after leaving the car (seconds) is set to how many seconds it will take to unlock the car after the car leaves the car. The default value is 20, and the range is 0-60. | Yes |
lockEnabledDate0 | Ground lock activation time period (0:00-8:00). Ground lock activation time period, every half hour is 1 unit, every 8 hours is a group; activation: raise the ground lock, deactivation: lower the ground lock Example: 65535 converted to binary is 1111111111111111, which means 0:00-8:00 is fully open | Yes |
lockEnabledDate1 | Same as above | Yes |
lockEnabledDate2 | Same as above | Yes |
localWhiteList | localWhiteList: { { "plate": "", "localWhiteOpt": number //0:none 1:add 2:del } } 0 means no processing, 1 means adding, 2 means deleting |
Yes |
localWhiteNum | Number of license plates issued | Yes |
authMode | Authentication mode: 0 - automatic mode (default) (camera judgment); 1 - manual mode (except for local whitelist license plates, everyone must authenticate with the platform); 2 - special rules (except for local whitelist license plates, only blue license plates are authenticated). The authentication mode is used by the platform to switch the device's access policy to the vehicle: Automatic mode (default): The camera makes the judgment based on the license plate recognition results and only allows all new energy vehicles to enter (i.e. the logic is implemented in the first phase of the project). When the vehicle leaves, the device performs logical processing according to the rules of the enabled time period (enabled = > upgraded); Manual mode: Locally saved whitelist license plate unlocking; all non-whitelist vehicles apply for authentication to the platform, and the device does not perform active unlocking logic. After the device detects the vehicle and reports the license plate number, the platform will actively send a unlocking command. When the vehicle leaves, the device performs logical processing according to the enabled time period rules (enabled = > up); Special rules: Locally saved whitelist license plates will be unlocked, non-whitelist new energy license plates will be unlocked; when a non-whitelist blue license plate vehicle enters, the device will not perform automatic unlocking logic. After the device detects the vehicle and reports the license plate number, the platform will actively send a unlocking command. When the vehicle leaves, the device will perform logical processing according to the enabled time period rules (enabled = > upgraded); Policy Priority: Platform control ground lock mode (forced rise and fall) > authentication mode; When the authentication mode is executed, the lock-up logic: platform-controlled ground lock mode (forced up and down) > executed according to the working time period; |
Yes |
taskPhotosDuration | Timing snapshot interval (unit: seconds, minimum value: 10) | Yes |
buzzer | Buzzer (0 off, 1 on) | Yes |
Response message style
{ "operator": "GroundlockLiftStrategy-Ack", "sessionId": "SID:1234567890-000001", "messageId": "MID:localhost-122334455667-12232323232323-000001", "info": "none", "result": { "errorNo": 0, "description": "ok" } }